Event-pools: Consistency fix for vertexing#2297
Merged
Conversation
For event pools, the vertex applied to events should (0,0,0). We tried to do this by setting 'kNoVertex' to the collision context... which unfortunately was not doing what we wanted. Instead of putting (0,0,0) this simply does not put a vertex into the collision context. This lead to the consequence that the vertex was fixed during event generation later. Problem fixed by imposing `kNoVertex` also on the event generation step **in case of event pool generation**.
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For event pools, the vertex applied to events should (0,0,0). We tried to do this by setting 'kNoVertex' to the collision context... which unfortunately was not doing what we wanted. Instead of putting (0,0,0) this simply does not put a vertex into the collision context. This lead to the consequence that the vertex was fixed during event generation later.
Problem fixed by imposing
kNoVertexalso on the event generation step in case of event pool generation.